I am just trying out the Free Trial of SD.

Here in southern Germany I am unable to see the standard Airspace C starting at FL100.
I can see C starting at FL130 in the alpine area, but not the standard C in the flatlands.

Same goes with airspace E. Visible when the lower limit is off-standard (like 1000ft)
but not when standard (2500 ft).

What am I doing wrong? Thanks a lot!

(and yes, I have well planned a route high enough - currently FL150)

Very helpful. I am simply pointing out that if I implement this, the experience will get worse for just about every customer. This helps to explain why I have not implemented it.

I wasn't trying to be helpful just pointing out the expectation of your customers.

All I am saying is that airspace that requires an entry clearance is something most SD users expect to be warned about. Even if that airspace overlies an entire country at 10,000 feet (that's a reasonable VFR altitude, particularly in mountainous terrain). Climbing above 10,000 feet or crossing the German border at an altitude above 10,000 feet would have me in violation.

So if the standard way of checking for airspaces in SD isn't good enough for this, someone needs to be creative.


-- Chris.

Thank you Chris for pointing this out again!

I can only speak for myself (as a not-yet customer):
As long as SD only warns me about 95% of the relevant airspaces I will stick to my current solution and safe my money.

As you did not find Chrises "You'll figure it out" very helpful:

Obviously your software does not have any issues with thousands of airspaces in Europa that are currently NOT close to the coordinates of the airplane. I assume your software uses an algorithm that removes these airspaces in an initial step before checking for any airspace intrusions with the relevant (in close proximity) airspaces.

So why not split up the huge class C airspace in Germany in pre processing (NOT on the device)?
By breaking up these airspaces in maybe a frew dozen sub areas your software performance might be up again.